feat(engy): add engy provider - #5910

No actionable findings.

No actionable findings.

No actionable findings.

Endorsing this — I'm the owner of engy (api.engy.ai), and it's accurate.

I checked all seven files against what we serve. The prices, context/limit split, modalities, and reasoning controls are all correct — including the parts you can't verify externally: the authed input/output split (context = max_input + max_output), the per-deployment modality narrowing (qwen3.6 text-only; qwen3.8 / glm-5.3-flash / kimi-k3 text+image), kimi-k3 honoring temperature, the glm-5.3-flash launch-discount billing (0.135/0.45), and the recent glm-5.3 context bump + kimi-k3 30% price raise.

The sync safeguards are exactly right for our unauthenticated list: skipCreates (avoids limit.output = 0 files), deleteMissing: false (an empty/truncated 200 can't wipe hand-measured files), and price rounding so repricing doesn't churn.

engy.ai/pricing is the right doc link, since our /docs lists no models.

Great work — the probing and fixed-point tests are well above the bar.

Thanks for checking it line by line, and for confirming the parts that cannot be verified from outside. That settles the two questions the draft carried: the doc link stays on engy.ai/pricing, and the entry goes in from this fork rather than yours. I have updated the description to point at your comment.

Two things from the last few days that the entry now reflects, in case they are useful on your side: the sync module picked up glm-5.3's window going to 327,680 and kimi-k3's 30% raise on its own, which is what it is there for, and I re-checked all 21 prices, the seven limits and the modality lists against the live list this morning at build 0.2.19 with no drift.

One measurement you may want regardless of this PR: on qwen3.6-35b-a3b, when max_tokens ends the generation inside the thinking block, the response comes back with the partial thinking as content and finish_reason: "stop" rather than "length" (6/6 at cap 16, 5/5 at cap 200, across ten miners; at cap 3000 the answer is clean). A client that trusts finish_reason reads that as a completed turn. Same shape as the parser faults your own MINER.md documents for tool calls. Happy to send the request ids.

No actionable findings.

@crabbytt deepseek-v4.1-flash is on the entry now (head 828aa15, bot clean). Same sources as before: 0.04 / 0.08 / 0.008 from /v1/models, 262,144 in and 65,536 out from the authenticated list, text+image checked by sending an image.

Two things only you can settle:

• Effort. On 0.2.20, low, medium and high measure as one rung and xhigh and max as another (n=40 per level, high vs max paired p=1e-04), the same shape as 0731, so the file authors high|max. Your docs' DeepSeek V4 column sends low and high to different levels; if v4.1-flash is meant to get that mapping, low should separate from high, and at n=40 it does not.
• The toggle. On v4.1-flash both chat_template_kwargs.thinking and enable_thinking switch reasoning (40/40 each way); on 0731 enable_thinking still looked inert in the one check I ran today. The header names thinking, which both honour. Say if you would rather it named the other.

Two observations from the run, both on 0.2.20, in case they are useful: the x-engy-miner and x-engy-request-id headers are absent on every response slower than about 15 s (114 of 480; the body's x_engy block had them on the one slow response I checked), and completion_tokens_details.reasoning_tokens is 0 on responses with a full reasoning_content, while completion_tokens and the bill include them.

No actionable findings.

Thanks — four answers, and three of them changed something.

Effort. Taken. Both DeepSeek entries now carry low|high|max instead of the high|max I had narrowed to. Your explanation is the reason: if the level is rendered into the prompt as a sentence rather than enforced as a budget, a length test at n=40–126 was never going to resolve one rung from the next, so the narrowing rested on evidence that could not have shown otherwise. Your docs' mapping table settles which levels are distinct, and the entries now follow it: sent to DeepSeek V4, low and medium both arrive as low, high as high, xhigh and max as max — three levels.

One small discrepancy while you have it open: you wrote that medium collapses onto high, the model default. The table on engy.ai/docs (read 2026-09-19) puts medium on low for DeepSeek V4. It does not change the entry either way, since medium is a duplicate of another level in both accounts, but one of the two is wrong and it is your page.

The toggle. Both DeepSeek files and kimi-k3 already name chat_template_kwargs.thinking — that part was settled before you wrote. What was missing was why enable_thinking worked on v4.1-flash and looked inert on 0731, and the rewrite table answers it. The body says so now, and says thinking is the checkpoint's own interface and the one that stays right off engy.

The headers. Recorded as a known quirk with your reproduction, and the body points anyone re-measuring at the x_engy block. Nothing in the entry depends on it.

reasoning_tokens. Noted, thank you. models.dev carries no field for it, so nothing changes here, but it matters for anyone measuring against engy.

No actionable findings.

@crabbytt @andy-engy kimi-k3's limits have changed, and the entry now follows them (head 1fac351).

• /v1/models reports context_length 1,113,088, up from 1,048,576.
• The authenticated list gives the split as max_input_tokens 1,047,552 (983,040 when I last checked on 2026-08-30) and max_output_tokens 65,536 (unchanged). The two add up to the new context exactly.
• The file now sets context = 1_113_088 explicitly, since it is above the lab's 1M window and can no longer be inherited.

I can't tell when between 08-30 and today this changed. An earlier version of this comment said it happened today, but I got that from the created field, which turns out to be the request time.

The other seven models match your pricing page and both model lists exactly, on price and on limits. If the larger prompt budget is not meant to stay, tell me and I'll put it back.

I have left MiniMax-H3 out of this PR. It is billed per second of video, and the catalogue only has per-token pricing.

No actionable findings.

No actionable findings.

No actionable findings.

@crabbytt I've split this PR. It now adds only the engy provider and its eight model files (head 939b47f, rebased on today's dev). The sync module will come as a separate PR once the provider is merged.

The reason is that it had been sitting clean for a month. Since late August, 25 of the 79 bot-approved provider-only PRs here have been merged, and 0 of the 9 that bundled a sync module. Sync modules for providers already in the catalogue have been getting merged within days as their own PRs, so that's the route I'm taking.

Nothing in your entry has changed. The model files are byte-identical to the version you endorsed, plus today's kimi-k3 limits (above). Until the sync PR lands, prices and context are updated by hand. If you change something in the meantime, a note here is enough and I'll pick it up.

No actionable findings.